<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PropertyBlankRendering</key>
<dict>
<key>Description</key>
<string>Check if a message doesn't render anything - most of the time the message is an ill-formed email with attachments.</string>
</dict>
<key>PropertyDateInFuture</key>
<dict>
<key>Description</key>
<string>Check if the date/time a message was sent is in the future (resolution is in minutes). Due to different timezones it is a rather common mistake made by spammers. (default setting is 120 minutes ahead)</string>
<key>View</key>
<string>propertyDateInFutureView</string>
</dict>
<key>PropertyDateInThePast</key>
<dict>
<key>Description</key>
<string>Check if the date/time a message was sent is in the past (resolution is in days). This tends to happen less frequently than the "date-in-the-future" property. If you don't check your emails often, you may want to turn off this test to avoid false positives. (default setting is 2 days in the past)</string>
<key>View</key>
<string>propertyDateInThePastView</string>
</dict>
<key>PropertyDateMalformed</key>
<dict>
<key>Description</key>
<string>Well-implemented/configured email clients should send out emails with datestamps in a correct format.</string>
</dict>
<key>PropertyDateMissing</key>
<dict>
<key>Description</key>
<string>Check if a message comes with no datestamp. This is a pretty reliable sign of junk mails.</string>
</dict>
<key>PropertyDomainNoMX</key>
<dict>
<key>Description</key>
<string>Check if there is any MX (Mail Exchange) server listed with the domain of the sender address; it is effective to find bogus domain of a sender address. This property requires Internet connection for query (DNS lookups), and in some rare cases may take up to 10 seconds to complete.</string>
</dict>
<key>PropertyHTMLAttachment</key>
<dict>
<key>Description</key>
<string>Check if a message has any HTML attachment. If you only want to pay attention to plain-text emails, turn on this test.</string>
</dict>
<key>PropertyHTMLBadTags</key>
<dict>
<key>Description</key>
<string>Check if an HTML-based message contains too many bad tags. Spammers often use bogus HTML tags to break up words or to confuse junk filter. You can define what tags are legal. (default setting is 5)</string>
<key>View</key>
<string>propertyHTMLBadTagsView</string>
</dict>
<key>PropertyHTMLHiddenURLs</key>
<dict>
<key>Description</key>
<string>Check if an HTML-based message contains too many hidden URLs. Spammers often use hidden URLs to "poison" junk filters that collect such URLs. You can define what attributes of what HTML tags can take URLs. (default setting is 1)</string>
<key>View</key>
<string>propertyHTMLHiddenURLsView</string>
</dict>
<key>PropertyHTMLVacuousTags</key>
<dict>
<key>Description</key>
<string>Check if an HTML-based message contains too many tags that render nothing (e.g., a pair of "<font></font>" tags will render nothing). Spammers sometimes use this to break up words. (default setting is 3)</string>
<key>View</key>
<string>propertyHTMLVacuousTagsView</string>
</dict>
<key>PropertyHasBadSites</key>
<dict>
<key>Description</key>
<string>Check if URLs mentioned in the body and the subject of a message match any "bad site" collected from the previously seen junk mails. The bad sites are automatically collected from the filtered emails: you can check the collection by opening the Sites window. This is a very useful property and should probably be turned on at all times.</string>
<key>View</key>
<string>propertyHasBadSitesView</string>
</dict>
<key>PropertyMessageIDMalformed</key>
<dict>
<key>Description</key>
<string>A message ID is almost always found in the header of a message, and it looks something like <something@some.domain.name>. A malformed message ID is a pretty reliable indicator that the message is junk.</string>
</dict>
<key>PropertyMessageMalformed</key>
<dict>
<key>Description</key>
<string>A malformed email is usually not viewable, or it might have "\0" character in it (to exploit weakness of certain client software). It should always be thrown away. This is a mandatory test.</string>
</dict>
<key>PropertyOpenRelay</key>
<dict>
<key>Description</key>
<string>Check if any IP address mentioned in the header of a message matches known spamming IPs from a specified number of blacklists. This test requires Internet connection for query (DNS lookups). You can choose up to 3 blacklists to query, and define what are "safe IPs" that should not be checked.</string>
<key>View</key>
<string>propertyOpenRelayView</string>
</dict>
<key>PropertyPhishingURL</key>
<dict>
<key>Description</key>
<string>Check if an HTML-based message contains at least a phishing URL. A "phishing" URL is a link pointing to a place different from what it claims to. Optionally you can check whitelisted emails too so they will get filtered if they contain phishing URLs. This is a very useful property and should probably be turned on at all times.</string>
<key>View</key>
<string>propertyPhishingURLView</string>
</dict>
<key>PropertyRecipientMalformed</key>
<dict>
<key>Description</key>
<string>Similar to "malformed sender address", only to check the RFC2822 conformance of all recipient address(es).</string>
</dict>
<key>PropertyRecipientMissing</key>
<dict>
<key>Description</key>
<string>Check if the recipient ("to" or "cc") part of a message is missing.</string>
</dict>
<key>PropertyRecipientsMismatch</key>
<dict>
<key>Description</key>
<string>Check if a message doesn't even address you in the recipient list: if *none* of the patterns you specified is matched with the recipients of a message, it is classified as junk. IMPORTANT: you need to set up the possible email addresses that people will use to send emails to you.</string>
<key>View</key>
<string>propertyRecipientsMismatchView</string>
</dict>
<key>PropertyRecipientsTooMany</key>
<dict>
<key>Description</key>
<string>Check if the number of recipients ("to" and "cc") exceeds a certain number. Mass-mailing of one single message often is a telltale sign of junk emails. You should set the threshold value carefully. (default setting is 5 recipients)</string>
<key>View</key>
<string>propertyRecipientsTooManyView</string>
</dict>
<key>PropertySenderMalformed</key>
<dict>
<key>Description</key>
<string>Check if the sender address conforms with RFC2822. A malformed sender address is almost always a reliable indicator that the message is junk.</string>
</dict>
<key>PropertySubjectMissing</key>
<dict>
<key>Description</key>
<string>Check if a message comes with no subject.</string>
</dict>
<key>PropertyTooFewKnownRecipients</key>
<dict>
<key>Description</key>
<string>Check if the number of "known" recipients (other than yourself) of a message is fewer than a specified number: if yes the message is classified as junk. This property uses the data you entered in the Address Book to determine whether a recipient is known or not. (default setting is 1)</string>
